Skip to content

chore(versions): Bump for 2.19.1#578

Merged
benjaminpkane merged 4 commits into
release/v2.19.1from
bump-versions-2.19.1
May 29, 2026
Merged

chore(versions): Bump for 2.19.1#578
benjaminpkane merged 4 commits into
release/v2.19.1from
bump-versions-2.19.1

Conversation

@benjaminpkane

Copy link
Copy Markdown
Member

What

Bumps version references from 2.19.02.19.1 for the release/v2.19.1 patch release.

Generated via:

for file in $(ack -l '2\.19\.0'); do
  perl -pi -e 's/2\.19\.0/2.19.1/g' "$file"
done
git restore tests/fixtures/**

Scope

Updated: READMEs, docs, docker compose files, Helm chart files (Chart.yaml, values.yaml, values.schema.json, README.md), Makefile, skaffold.yaml, and the compose unit tests.

Intentionally excluded

  • tests/fixtures/** — restored after the bump. Automation updates these as new RC artifacts become available; bumping them early would make automation pull artifacts that don't yet exist.
  • .tool-versions — the skaffold 2.19.0 pin is the skaffold tool version (independent of the FiftyOne app version; it was already 2.19.0 during the 2.18.1 release) and is left unchanged.

🤖 Generated with Claude Code

Update version references from 2.19.0 to 2.19.1 across READMEs, docs,
docker compose files, Helm chart files, and compose unit tests. Test
fixtures are intentionally not bumped; they are updated by automation as
RC artifacts become available. The skaffold tool pin in .tool-versions
is left unchanged (it is the skaffold version, not the app version).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@benjaminpkane benjaminpkane requested a review from a team as a code owner May 29, 2026 15:27
@coderabbitai

coderabbitai Bot commented May 29, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c8166369-c268-4523-810a-962e7b5acde4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Walkthrough

This PR performs a uniform version bump from FiftyOne 2.19.0 to 2.19.1 across the repository. The Makefile version variable is updated, followed by corresponding updates to Docker image tags, environment variable values, and SDK version references in deployment documentation, upgrade guides, and unit test assertions.

Changes

Version Bump to 2.19.1

Layer / File(s) Summary
Build system version definition
Makefile
The VERSION make variable is updated from 2.19.0 to 2.19.1.
Deployment documentation and examples
docker/README.md, docker/docs/configuring-gpu-workloads.md, docs/custom-plugins.md, docs/orchestrators/configuring-databricks-orchestrator.md, docs/orchestrators/configuring-kubernetes-orchestrator.md, helm/fiftyone-teams-app/README.md
Docker image override examples, Kubernetes telemetry sidecar templates, Databricks orchestrator requirements, and Helm chart version badge/SDK recommended version documentation are updated to reference v2.19.1 and fiftyone==2.19.1.
Upgrade guides
docker/docs/upgrading.md, helm/docs/upgrading.md
FiftyOne Enterprise and Teams upgrade instructions across multiple upgrade paths are updated to target version 2.19.1, including SDK version requirements, telemetry sidecar references, license file prerequisites, and connectivity warnings.
Unit test assertions
tests/unit/compose/docker-compose-internal-auth_test.go, tests/unit/compose/docker-compose-legacy-auth_test.go
Expected Docker Compose image tags and FIFTYONE_APP_TEAMS_SDK_RECOMMENDED_VERSION environment variable values are updated from v2.19.0 / 2.19.0 to v2.19.1 / 2.19.1 across test cases for all service types and authentication variants.

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly Related PRs

Suggested Labels

priority-low

Suggested Reviewers

  • kevin-dimichel
  • mo-getter

Poem

🐰 From 2.19.0 to 2.19.1 they hop,
Version strings dance without a stop,
Docs and tests all fall in line,
Each little bump makes things align! ✨

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name Status Explanation Resolution
Linked Issues check ⚠️ Warning The linked issue #39 requires renaming .yml files to .yaml, but this PR only performs version bumping and does not address the filename changes specified in the linked issue. Address issue #39 by renaming ./.github/workflows/release.yml to ./.github/workflows/release.yaml (or with a hyphen separator if desired) or clarify why this is not included in this PR.
Description check ❓ Inconclusive The PR description explains the changes well but does not follow the required template structure with sections like 'Rationale', 'Changes', and 'Testing', nor does it include priority or checkbox selections. Fill out the required template sections including Review Priority, the Changes checklist about Docker Compose/Helm parity, and the Testing section describing how changes were validated.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The PR title 'chore(versions): Bump for 2.19.1' clearly and concisely describes the main change: version bumping across the repository for the 2.19.1 release.
Out of Scope Changes check ✅ Passed All changes in the PR are within scope—they consist entirely of version bumps from 2.19.0 to 2.19.1 across documentation, Docker Compose files, Helm charts, Makefile, and unit tests, which aligns with the stated objective of preparing the 2.19.1 patch release.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch bump-versions-2.19.1

Comment @coderabbitai help to get the list of available commands and usage tips.

@kevin-dimichel kevin-dimichel self-requested a review May 29, 2026 18:35

@kevin-dimichel kevin-dimichel left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for making the release branch and updating the versions! You did the right thing by following the docs in setting the versions.

However, let's not change the version where we introduce the telemetry features (v2.19.0). This will prevent us from carrying forward those version updates in future releases.

Please apply the suggestions. After that, Aloha can approve this PR.

Comment thread docker/docs/upgrading.md Outdated
Comment thread docker/docs/upgrading.md Outdated
Comment thread helm/docs/upgrading.md Outdated
benjaminpkane and others added 3 commits May 29, 2026 16:44
Co-authored-by: Kevin DiMichel <56850465+kevin-dimichel@users.noreply.github.com>
Signed-off-by: Benjamin Kane <ben@tapes.co>
Co-authored-by: Kevin DiMichel <56850465+kevin-dimichel@users.noreply.github.com>
Signed-off-by: Benjamin Kane <ben@tapes.co>
Co-authored-by: Kevin DiMichel <56850465+kevin-dimichel@users.noreply.github.com>
Signed-off-by: Benjamin Kane <ben@tapes.co>

@kevin-dimichel kevin-dimichel left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@benjaminpkane benjaminpkane merged commit e8aca2b into release/v2.19.1 May 29, 2026
10 of 12 checks passed
@benjaminpkane benjaminpkane deleted the bump-versions-2.19.1 branch May 29, 2026 21:41
@coderabbitai coderabbitai Bot mentioned this pull request Jun 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants